Skip to main content

Home/ IMT122 OUA Group/ Group items tagged Week 06

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Joanne S

The Code4Lib Journal - How Hard Can It Be? : Developing in Open Source - 0 views

journal.code4lib.org/...1638

IMT122 Essential Reading Week 06 Task 06 Koha

shared by Joanne S on 02 Oct 12 - Cached
  • We experienced freedom to explore alternate avenues, to innovate, to take risks in ways that would have been difficult under the direct control of a district council.
  • patrons made it clear that while they appreciated that computers were a necessary part of a modern library, they did not consider them the most important part.
  • Our overall objective was to source a library system which: could be installed before Y2K complications immobilised us, was economical, in terms of both initial purchase and future license and maintenance support fees, ran effectively and fast by dial-up modem on an ordinary telephone line, used up-to-the minute technologies, looked good, and was easy for both staff and public to use, took advantage of new technology to permit members to access our catalogue and their own records from home, and let us link easily to other sources of information – other databases and the Internet. If we could achieve all of these objectives, we’d be well on the way to an excellent service.
  • ...14 more annotations...
  • "How hard can it be" Katipo staff wondered, "to write a library system that uses Internet technology?" Well, not very, as it turned out.
  • Koha would thus be available to anyone who wanted to try it and had the technical expertise to implement it.
  • fairly confident that we already had a high level of IT competence right through the staff, a high level of understanding of what our current system did and did not do.
  • ensure the software writers did not miss any key points in their fundamental understanding of the way libraries work.
  • The programming we commissioned cost us about 40% of the purchase price of an average turn-key solution.
  • no requirement to purchase a maintenance contract, and no annual licence fees.
  • An open source project is never finished.
  • Open source projects only survive if a community builds up around the product to ensure its continual improvement. Koha is stronger than ever now, supported by active developers (programmers) and users (librarians)
  • There are a range of support options available for Koha, both free and paid, and this has contributed to the overall strength of the Koha project.
  • Vendors like Anant, Biblibre, ByWater, Calyx, Catalyst, inLibro, IndServe, Katipo, KohaAloha, LibLime, LibSoul, NCHC, OSSLabs, PakLAG, PTFS, Sabinet, Strategic Data, Tamil and Turo Technology take the code and sell support around the product, develop add-ons and enhancements for their clients and then contribute these back to the project under the terms of the GPL license.
  • FRBR [5] arrangement, although of course it wasn’t called that 10 years ago, it was just a logical way for us to arrange the catalogue. A single bibliographic record essentially described the intellectual content, then a bunch of group records were attached, each one representing a specific imprint or publication.
  • The release of Koha 3.0 in late 2008 brought Koha completely into the web 2.0 age and all that entails. We are reconciled to taking a small step back for now, but the FRBR logic is around and RDA should see us back where want to be in a year or so – but with all the very exciting features and opportunities that Koha 3 has now.
  • In the early days, the Koha list appeared to have been dominated by programmers but I have noticed a lot more librarians participating now
  • "Adopt technology that keeps data open and free, abandon[ing] technology that does not." The time is right for OSS.
  • Joanne S on 02 Oct 12
     
    For more information about Koha and how it was developed, see: Ransom, J., Cormack, C., & Blake, R. (2009). How Hard Can It Be? : Developing in Open Source. Code4Lib Journal, (7). Retrieved from http://journal.code4lib.org/articles/1638
Joanne S

How to solve impossible problems: Daniel Russell's awesome Google search techniques - 0 views

www.johntedesco.net/...esome-google-search-techniques

IMT122 Reading List Week 04 Essential Reading Google Search Topic 04 IMT122

shared by Joanne S on 11 Sep 12 - No Cached
  • Most of what you know about Boolean is wrong.
  • Think about how somebody else would write about the topic.
  • Use language tools.
  • ...8 more annotations...
  • Use quotes to search for phrases.
  • Force Google to include search terms.
  • intext:”San Antonio” intext:Alamo
  • It forces Google to show results with the phrase “San Antonio” and the word Alamo. You won’t get results that are missing either search term.
  • Minus does not equal plus.
  • “Control F” is your friend
  • Limit the time frame.
  • Use this keyboard shortcut to find a word or phrase on any web page. I
Joanne S

Emerald | Evaluating and comparing discovery tools: how close are we towards next gener... - 0 views

www.emeraldinsight.com.dbgw.lis.curtin.edu.au/journals.htm

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases Discovery Layers Curtin Login Required

shared by Joanne S on 18 Sep 12 - Cached
  • Joanne S on 18 Sep 12
     
    (Curtin Login) Yang, S. Q., & Wagner, K. (2010). Evaluating and comparing discovery tools: how close are we towards next generation catalog? Library Hi Tech, 28(4), 690-709. doi:10.1108/07378831011096312 Retrieved from http://www.emeraldinsight.com.dbgw.lis.curtin.edu.au/journals.htm?articleid=1896437&show=abstract
Joanne S

Finding a fit: EDRMS and your organisation: Enhancements, consolidation and beyond. (E-... - 0 views

edocs.library.curtin.edu.au/eres_display.cgi

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases Records Management Curtin Login Required

shared by Joanne S on 18 Sep 12 - Cached
  • Joanne S on 18 Sep 12
     
    Records Management Systems. Whiting, J. (2007). Finding a fit: EDRMS and your organisation: Enhancements, consolidation and beyond. Informaa Quarterly, 23(3), 26-29. Retrieved from http://eres.lis.curtin.edu.au/cgi-bin/gw?url=dc60250138
Joanne S

National Library of Australia IT Architecture Project Report - 0 views

wiki.nla.gov.au/...itag.pdf

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases

shared by Joanne S on 18 Sep 12 - Cached
  • Joanne S on 18 Sep 12
     
    Advanced Reading about integrating information in many databases into one access point. National Library of Australia. (2007). National Library of Australia IT Architecture Project Report. Canberra, A.C.T.: National Library of Australia. Retrieved from http://www.nla.gov.au/dsp/documents/itag.pdf
Joanne S

What is a Database, really? Data Storage for Librarians « The Other Librarian - 0 views

otherlibrarian.wordpress.com/...ly-data-storage-for-librarians

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases Libraries

shared by Joanne S on 18 Sep 12 - Cached
  • A Text File Good old text is still not a bad way to store data. 
  • If you want to retrieve that information, you can use a script to tell the computer to organize the information in a particular way.   This is called parsing
  • Structured Text As you climb the data food chain, complex systems get developed to organize information. 
  • ...17 more annotations...
  • Mark-up:   Marked information is data that has marks or signals to let a computer distinguish one type of data from the other.  
  • A variable:   A variable happens when you give some data a name. 
  • A string:   A string is a kind of variable that has text.
  • An array:   An array is a type of variable that includes a list used by computer programs for later manipulation.    
  • An object:   Explaining objects in full requires that someone read up on object-oriented programming.  
  • Tree-based  Structures Tree-based structures, or cluster models are a subset of “structured text” data storage models.  
  • XML is probably the best example.
  • data is organized in “parents”, “siblings” and “children”.
  • The Relational Model The relational model is better than a tree-model when your dataset is large and complicated.    The way it works is, instead of thinking in terms of “parents, siblings and children,” you think in term of relationships.
  • the “Primary Key.”   This means that every data object (such as a library) has a way of identifying itself in a unique way
  • a “Foreign Key.”    The Foreign key is a way to associate one dataset (eg. libraries) with another dataset (eg. library branches, hospitals or businesses).
  • This association is called a relationship.
  • In more complicated relationships (called the Many-to-Many relationship), you might have to create a third table to associate two entities.      
  • TEXT/XML Based Text files can be organized in such a way as to accommodate some of the benefits of the relational model.
  • Two examples of XML-based databases include Xindice and Sedna.
  • SQL/Binary-based Databases The more common relational database type is a piece of software running on a server, rather than a set of text files.   They are generally accessed using a standard language called SQL (Structure Query Language), or more specifically SQL as supported by a popular scripting language like PHP, Python or Java.
  • Almost any major web application will have a combination of all these types of data storage methods!  
  • Joanne S on 18 Sep 12
     
    How databases are used in libraries
Joanne S

Database design basics - Access - Office.com - 0 views

office.microsoft.com/...design-basics-HA001224247.aspx

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases

shared by Joanne S on 18 Sep 12 - Cached
  • Joanne S on 18 Sep 12
     
    Designing elements and database design
1 - 7 of 7
Showing 20▼ items per page